Can you detail what you mean with "the termination behavior (Ctrl C) for cmd scripts cannot be modifed"? What exactly doesn't work?

Hi Arcanis! You can see the discussion with Microsoft re cmd termination behavior in the linked bug. Short version is that cmd requires Ctrl C twice, and everyone on the cmd and console team at Microsoft firmly recommend new software not be made using cmd.

What do you think about microsoft/terminal#217 (comment)? It seems like a valid concern.

It seems to me that cmd scripts are generally used in the place of exe symlinks and shebang scripts, which PowerShell is not a good replacement for - if you switch out yarn.cmd for yarn.ps1, that's fine if you're already in PowerShell, but if you're in cmd, or some other shell, or using ShellExecute or some scripting language's equivalent, you have to write pwsh -c yarn, so then why not get rid of the script altogether and do node yarn.js?

@arcanis Comment is accurate but doesn't affect anything:

• Yes, if I was calling yarn.js from something other than the command line, I'd call node yarn.js and not use yarn.ps1.
• In the exact same way, right now, if I was calling yarn.js from something other than the command line, I'd call node yarn.js and not use yarn.cmd.

The purpose of the ps1 or cmd file is a quick alias to be run from the shell. The default shell in Windows is Powershell (see Win X). Powershell is also the only maintained shell, according to the cmd authors. Moving to powershell (as well as fixing termination issues) means that when something goes wrong we don't have to debug an unsupported shell.

I'm the one with the concerned comment. I just did an experiment and found that PowerShell will pick a .ps1 file before a .cmd, so rather than replace the script, can you just add the PowerShell script? That should give you working ^C behavior in PowerShell without breaking cmd.

@mikemaccana quick question - are you proposing that the .cmd file still be retained?

I followed the discussion here and came to this issue. I created a yarn.ps1 file in my yarn installation folder and then ran yarn. It works very well! Ctrl+C doesn't ask the question Terminate batch job (Y/N)?. So I imagined that we could remove the .cmd file and the .ps1 file would be enough.

But if I remove the yarn.cmd file, then the yarn.ps1 script fails - it opens up yarn.js in my text editor instead! This is a slightly weird side-effect.

@kumarharsh not sure what the purpose of the cmd file would be. yarn.ps will help default command line users, node can run the yarn.js itself. Only reason I could see if for users who explicitly launch cmd as an interactive terminal in 2018 - most of those are probably doing that out of ignorance so education might be better.

Are you using the ps1 from this commit, or a file you made?

I created a ps1 file with the contents of this PR. It's weird that removing the cmd file stops the ps1 file from working - I'm using pwsh as my default shell fwiw.

Only reason I could see if for users who explicitly launch cmd as an interactive terminal in 2018 - most of those are probably doing that out of ignorance so education might be better.

Fwiw I hate* powershell even more than I hate cmd, so I tend to use cmd at home. I doubt I'm the only one, so I'd say it's safer to keep both.

(*) Hate is a strong word tbh, it's just that I never got the time to learn the Powershell syntaxes, and I mostly use WSL nowadays anyway, so it's not a priority.

Keeping yarn.cmd is definitely the safer option.

A common method of determining whether a file is executable in Windows is to compare its file extension with the extensions listed in the PathExt environment variable. PS1 is typically not in that list, but CMD is.

node-which is one example of a library that uses this method. If yarn.cmd was removed, then anything that uses node-which directly to find the yarn executable would instead find yarn.js (because .JS is typically in PathExt, after .CMD). If they then tried to execute yarn.js directly on Windows, it would blow up. Libraries like cross-spawn are smart enough to also read the shebang from yarn.js and execute it with node instead, but... a shebang is not conventional in Windows, and most libraries aren't as smart as cross-spawn. It's conceivable that removing yarn.cmd would break things, even putting cmd.exe interactive terminal users aside.

As requested, I've updated the PR and left yarn.cmd for any people still running cmd.

Relevant discussion on npm: npm/rfcs#20

Perfect, thanks!

I use cmd because I don't like powershell, but also because && doesn't work in powershell [1] and there are a lot of package.json files out there that utilize this very handy trick to run 2 different commands from the same scripts entry (e.g. "prepublish": "./node_modules/.bin/projectz compile && npm test").

[1] npm/npm#4040 (comment)

@waynebloss npm always uses cmd for scripts, even when running them from PowerShell.

@felixfbecker OK, thanks. I'm not sure if that was always the case or not - I've been using Node since very early on in Windows and well, regardless of what I do with powershell I always have problems :)